Cohort file upload regression tests in jMeter #145
Merged
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Description
Created a performance test for Uploading Cohort Data in jMeter, which will upload a user-defined file, from a user-defined directory (both defined in the CLI). Once the file has been uploaded it will then poll every second until it has processed properly, this will give an idea for the end-user as to how long it takes to successfully upload and process a file. This therefore wouldn't really require going through logs in the backend to collate how long it took. There is no limit on the file length upload and has tested a 15k dataset. There could be some further improvements to the entire flow, such as creating a dataset before the test runs and the script picks it up, but this is the MVP right now.
Context
Test is required for further level of testing across the platform, as this area isn't currently covered in regression testing
Type of changes
Checklist
Sensitive Information Declaration
To ensure the utmost confidentiality and protect your and others privacy, we kindly ask you to NOT including PII (Personal Identifiable Information) / PID (Personal Identifiable Data) or any other sensitive data in this PR (Pull Request) and the codebase changes. We will remove any PR that do contain any sensitive information. We really appreciate your cooperation in this matter.